home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20010921-20020314
/
000382_jaltman@watsun.cc.columbia.edu_Wed Feb 20 09:15:48 EST 2002.msg
< prev
next >
Wrap
Text File
|
2002-03-13
|
3KB
|
68 lines
Article: 13228 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!watsun.cc.columbia.edu!jaltman
From: jaltman@watsun.cc.columbia.edu (Jeffrey Altman)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: K95 crashes PC when interrupted
Date: 20 Feb 2002 13:33:01 GMT
Organization: Columbia University
Lines: 51
Message-ID: <a508id$aho$1@newsmaster.cc.columbia.edu>
References: <3c737ea4.9852747@news.ision.net.uk>
NNTP-Posting-Host: watsun.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1014211981 10808 128.59.39.2 (20 Feb 2002 13:33:01 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 20 Feb 2002 13:33:01 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:13228
I have a few possible theories. However, the reality is, an Operating
System should not be brought down by an application. If you are getting
VxD errors (which VxD?) then it is most likely there is something wrong
with the serial driver provided by Microsoft when a thread is allowed
to end before data given to the driver to send has actually been sent.
In article <3c737ea4.9852747@news.ision.net.uk>,
Rob S <robatwork@REMOVEmail.com> wrote:
: Hi,
:
: I have setup the following scenario:
:
: Win 98 PC running K95 1.1.20 connected to DOS PC running msk3.14 via 3 wire
: serial cable. K95 is initiated from a batch file COMMS.BAT, which amongst other
: things contains the line:
: K95 commandfile
:
: commandfile contains various paramaters such as
: set port 1
: set speed 57600
: get file1
: send file2
: bye
:
: Comms works fine when DOS PC in in server mode.
:
: When Comms is interrupted with Ctrl-C, very odd things happen to the PC. About a
: minute after pressing Ctrl-C (which interrupts the comms correctly), the PC
: blue-screens with VxD errors. Or it reboots itself. Or locks up. Never
: immediately, but consistently crashes one way or another.
:
: If Comms is allowed to finished correctly, the PC is rock solid. In day to day
: use the PC crashes no more than normal for a Win 98 box. The problem is
: definitely after interrupting K95 with Ctrl-C.
:
: I'm continuing my investigations, as I *think* this only happens when K95 is run
: with the commandfile. As a workaround so far I have
: set transfer interrupt off which disables Ctrl-C.
:
: Any ideas why it's crashing the PC?
:
: tia
: -Rob
: robatwork at mail dot com
Jeffrey Altman * Sr.Software Designer C-Kermit 8.0 available now!!!
The Kermit Project @ Columbia University includes Telnet, FTP and HTTP
http://www.kermit-project.org/ secured with Kerberos, SRP, and
kermit-support@columbia.edu OpenSSL. Interfaces with OpenSSH